Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 1670946ea9567a100a53d2a65724ea594e587a20f4aaad30ef943d43131e1f70

Tx prefix hash: fc0d19fd968cfc6960de0a6a06ba626c89e8b98153c1680198a6b4843b6220b9
Tx public key: 8fad28cf45433aa0b39b6f288a5e330b970ea0816091f40bd7d6d7e0c103927a
Timestamp: 1731520437 Timestamp [UCT]: 2024-11-13 17:53:57 Age [y:d:h:m:s]: 00:131:06:17:15
Block: 1152970 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93626 RingCT/type: yes/0
Extra: 018fad28cf45433aa0b39b6f288a5e330b970ea0816091f40bd7d6d7e0c103927a02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1cf73c5167c500a52ec46849373588a4272f081fd7be53bd2f2c08a16468c43 0.600000000000 1638577 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1152980, "vin": [ { "gen": { "height": 1152970 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1cf73c5167c500a52ec46849373588a4272f081fd7be53bd2f2c08a16468c43" } } ], "extra": [ 1, 143, 173, 40, 207, 69, 67, 58, 160, 179, 155, 111, 40, 138, 94, 51, 11, 151, 14, 160, 129, 96, 145, 244, 11, 215, 214, 215, 224, 193, 3, 146, 122, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8