Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a02ffdea0c3e1b24ca30486e93d77ee4ac1ed9b4eeb077068aef1c8bf53e296

Tx prefix hash: f9455c8802f119de75e0c1c4f53f11df301bef04a7eb51928050da7a39d92291
Tx public key: f1f464d067331ed121f8c899dd69bd2d24abfecf8c085c7b3b9cc2e03716e149
Timestamp: 1738282428 Timestamp [UCT]: 2025-01-31 00:13:48 Age [y:d:h:m:s]: 00:042:15:31:49
Block: 1208708 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30517 RingCT/type: yes/0
Extra: 01f1f464d067331ed121f8c899dd69bd2d24abfecf8c085c7b3b9cc2e03716e1490211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 722537c1693152849a6f579fa664b5aa187a4e24f4af747dfc68c03c06e294e2 0.600000000000 1695441 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": 1208718, "vin": [ { "gen": { "height": 1208708 } } ], "vout": [ { "amount": 600000000, "target": { "key": "722537c1693152849a6f579fa664b5aa187a4e24f4af747dfc68c03c06e294e2" } } ], "extra": [ 1, 241, 244, 100, 208, 103, 51, 30, 209, 33, 248, 200, 153, 221, 105, 189, 45, 36, 171, 254, 207, 140, 8, 92, 123, 59, 156, 194, 224, 55, 22, 225, 73, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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