Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf3d87a5967aac3c8360025d6d495ade3e17b56f4c47b14f83d954b6ac8a907c

Tx prefix hash: 80c59f3ed2a02141ced689842886684092034113e5dbe13859f4cc1059b2ecd2
Tx public key: b3e0448f51ea10e4aa63c90bd56c680e478e19580722dc44f88354f526e3a438
Timestamp: 1748885881 Timestamp [UCT]: 2025-06-02 17:38:01 Age [y:d:h:m:s]: 00:220:12:22:01
Block: 1296487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155363 RingCT/type: yes/0
Extra: 01b3e0448f51ea10e4aa63c90bd56c680e478e19580722dc44f88354f526e3a43802110000000143846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f223cfd645fdee5a5320df0f58cb633f344ecb7eafc72195b11d318c18bb1cf 0.600000000000 1783998 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": 1296497, "vin": [ { "gen": { "height": 1296487 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f223cfd645fdee5a5320df0f58cb633f344ecb7eafc72195b11d318c18bb1cf" } } ], "extra": [ 1, 179, 224, 68, 143, 81, 234, 16, 228, 170, 99, 201, 11, 213, 108, 104, 14, 71, 142, 25, 88, 7, 34, 220, 68, 248, 131, 84, 245, 38, 227, 164, 56, 2, 17, 0, 0, 0, 1, 67, 132, 109, 102, 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