Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 161fcd8d0ee2cbac48ec0ca4c079b1bd79586516ab5a3abc6287f4a0ef24471f

Tx prefix hash: 70a623f013b7a03c1a27180d1f533c9da11f01a1db03188fe6167981a3cd9136
Tx public key: fd58b236c9fd4421c55c62e878c8336b1264d96c2bb58935b98c1d696e5ded93
Timestamp: 1727968913 Timestamp [UCT]: 2024-10-03 15:21:53 Age [y:d:h:m:s]: 00:211:09:17:08
Block: 1123629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150884 RingCT/type: yes/0
Extra: 01fd58b236c9fd4421c55c62e878c8336b1264d96c2bb58935b98c1d696e5ded9302110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fdcef5708ca2e1bf1f7005fbbd0c8669f05511cd3266967d1ae5ddec08f5064 0.600000000000 1606164 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": 1123639, "vin": [ { "gen": { "height": 1123629 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fdcef5708ca2e1bf1f7005fbbd0c8669f05511cd3266967d1ae5ddec08f5064" } } ], "extra": [ 1, 253, 88, 178, 54, 201, 253, 68, 33, 197, 92, 98, 232, 120, 200, 51, 107, 18, 100, 217, 108, 43, 181, 137, 53, 185, 140, 29, 105, 110, 93, 237, 147, 2, 17, 0, 0, 0, 11, 145, 225, 60, 4, 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