Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b123f173716b0d316c72d8a865183c0bb6407def43e67aa7dcb5126726403a16

Tx prefix hash: 8fc5dfe461d9e6c98ed8a59b2feaeb7f7fc7c26a73511186c519ea89a7be532a
Tx public key: 8e821f53e0329999c5a1721817ed5d043f6412017442e3f6dbdf355ac5434b16
Timestamp: 1720374673 Timestamp [UCT]: 2024-07-07 17:51:13 Age [y:d:h:m:s]: 00:261:05:39:54
Block: 1060656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186632 RingCT/type: yes/0
Extra: 018e821f53e0329999c5a1721817ed5d043f6412017442e3f6dbdf355ac5434b160211000000028fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e08b137e84e6f58c19a16ad9300ef5a19aa9ce4ad6df0af76e36910893da88f 0.600000000000 1531141 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": 1060666, "vin": [ { "gen": { "height": 1060656 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e08b137e84e6f58c19a16ad9300ef5a19aa9ce4ad6df0af76e36910893da88f" } } ], "extra": [ 1, 142, 130, 31, 83, 224, 50, 153, 153, 197, 161, 114, 24, 23, 237, 93, 4, 63, 100, 18, 1, 116, 66, 227, 246, 219, 223, 53, 90, 197, 67, 75, 22, 2, 17, 0, 0, 0, 2, 143, 218, 155, 45, 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