Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 133bd63ba109f7d847c798e98b0b3f42a2320a366917c3a489f58e72c450b5ff

Tx prefix hash: 3bbc6d9a2e3c76de7116352628022feabe78d0d59bb028cbfaae866fa5def04d
Tx public key: 43d2ae332a8dcf099df60d92be257b50596cc060e120308a7a5cf50fe8dba80e
Timestamp: 1765650347 Timestamp [UCT]: 2025-12-13 18:25:47 Age [y:d:h:m:s]: 00:008:22:55:14
Block: 1432885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6404 RingCT/type: yes/0
Extra: 0143d2ae332a8dcf099df60d92be257b50596cc060e120308a7a5cf50fe8dba80e021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c38b4f9674a7dccaa6b1a7333cb25c98f4405ee659ba0da0c7ef2cca26c628c0 0.600000000000 1921664 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": 1432895, "vin": [ { "gen": { "height": 1432885 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c38b4f9674a7dccaa6b1a7333cb25c98f4405ee659ba0da0c7ef2cca26c628c0" } } ], "extra": [ 1, 67, 210, 174, 51, 42, 141, 207, 9, 157, 246, 13, 146, 190, 37, 123, 80, 89, 108, 192, 96, 225, 32, 48, 138, 122, 92, 245, 15, 232, 219, 168, 14, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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