Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05b3089d2f0dabecde54f4be272c1b640865a73fa10350a693ebf3c75afd4951

Tx prefix hash: bfc5a518dfdb190b856fd311a1834f53942343e5ef892fcf6cbbf745e0a154a5
Tx public key: fbd9f98c88b0146243d3de263ba925acd2634da45951e48c6b8a9cf4f77f2750
Timestamp: 1736223237 Timestamp [UCT]: 2025-01-07 04:13:57 Age [y:d:h:m:s]: 00:099:13:30:25
Block: 1191909 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70952 RingCT/type: yes/0
Extra: 01fbd9f98c88b0146243d3de263ba925acd2634da45951e48c6b8a9cf4f77f275002110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4ab6020aaae0ba562af8bb06ded82bc50fdeab7e3862924dbdf5af7e918f02f 0.600000000000 1678452 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": 1191919, "vin": [ { "gen": { "height": 1191909 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4ab6020aaae0ba562af8bb06ded82bc50fdeab7e3862924dbdf5af7e918f02f" } } ], "extra": [ 1, 251, 217, 249, 140, 136, 176, 20, 98, 67, 211, 222, 38, 59, 169, 37, 172, 210, 99, 77, 164, 89, 81, 228, 140, 107, 138, 156, 244, 247, 127, 39, 80, 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