Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25f4a25f4f1c45fd2900453b1b87f82ccf946784c1dc327ed2fd83c765c42730

Tx prefix hash: 998fb5cc29d1ecbdfe380a39bec0b96936f2ce99fc55fb97c44909398812c178
Tx public key: 2fd259bc418a53aeeed34247cb05afd4b61dd24e9dcfbf9d34a6147696955383
Timestamp: 1721523160 Timestamp [UCT]: 2024-07-21 00:52:40 Age [y:d:h:m:s]: 00:095:01:34:57
Block: 1070181 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68064 RingCT/type: yes/0
Extra: 012fd259bc418a53aeeed34247cb05afd4b61dd24e9dcfbf9d34a61476969553830211000000010cce0636000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db9af358c2d5d2fc37de2d1a19c26fe7e51cb6dc4da3a146e9eebb2619d02a5a 0.600000000000 1541910 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": 1070191, "vin": [ { "gen": { "height": 1070181 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db9af358c2d5d2fc37de2d1a19c26fe7e51cb6dc4da3a146e9eebb2619d02a5a" } } ], "extra": [ 1, 47, 210, 89, 188, 65, 138, 83, 174, 238, 211, 66, 71, 203, 5, 175, 212, 182, 29, 210, 78, 157, 207, 191, 157, 52, 166, 20, 118, 150, 149, 83, 131, 2, 17, 0, 0, 0, 1, 12, 206, 6, 54, 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