Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a391dceee1a370d0c54a3d1c9bca917b31aaff54e5f2dbf978d4c1720fbdc3ec

Tx prefix hash: 3e2574e782f563a16949e19aa2a131046ced290a3bb3740162c8c775c8c85fe0
Tx public key: 0b472941c0e45bfc1ef48dfd7b104a45a8435a6dc08aa836312dfa84a669107d
Timestamp: 1702444496 Timestamp [UCT]: 2023-12-13 05:14:56 Age [y:d:h:m:s]: 01:103:13:04:27
Block: 912037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335108 RingCT/type: yes/0
Extra: 010b472941c0e45bfc1ef48dfd7b104a45a8435a6dc08aa836312dfa84a669107d02110000000575e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1678e0b094f2ab212eeb123b31c74d3d2af3d9f8473751cb8a3b529215d9e2ea 0.600000000000 1369255 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": 912047, "vin": [ { "gen": { "height": 912037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1678e0b094f2ab212eeb123b31c74d3d2af3d9f8473751cb8a3b529215d9e2ea" } } ], "extra": [ 1, 11, 71, 41, 65, 192, 228, 91, 252, 30, 244, 141, 253, 123, 16, 74, 69, 168, 67, 90, 109, 192, 138, 168, 54, 49, 45, 250, 132, 166, 105, 16, 125, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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