Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9eb016438b2ba0fc169bd542a58912e474e68fb10e370f1064d880c9193fd6cb

Tx prefix hash: 444b8b08fbe30cb87df6be88c8c964518c9653ea7d4a649a2f3ae7ede03f8993
Tx public key: 0b9821730e240cf5c2fbad2473dc1894563b288e45af27cd8f7e3df63989a1c7
Timestamp: 1730475004 Timestamp [UCT]: 2024-11-01 15:30:04 Age [y:d:h:m:s]: 00:140:14:16:31
Block: 1144314 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100312 RingCT/type: yes/0
Extra: 010b9821730e240cf5c2fbad2473dc1894563b288e45af27cd8f7e3df63989a1c7021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 784a834aac0532234b955e2e0e0eea3d350e1dadb8a5721e8410cb8a64008d0f 0.600000000000 1628489 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": 1144324, "vin": [ { "gen": { "height": 1144314 } } ], "vout": [ { "amount": 600000000, "target": { "key": "784a834aac0532234b955e2e0e0eea3d350e1dadb8a5721e8410cb8a64008d0f" } } ], "extra": [ 1, 11, 152, 33, 115, 14, 36, 12, 245, 194, 251, 173, 36, 115, 220, 24, 148, 86, 59, 40, 142, 69, 175, 39, 205, 143, 126, 61, 246, 57, 137, 161, 199, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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