Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64cb10e1efd9b86c3a1ce2560baf8ff76034a46014fa66443550848c6f7f41ac

Tx prefix hash: 78c332646736ec5ec2dec9967aa62c137c4b67da6d6635fba4a68735fc47a517
Tx public key: b55b23e0dfb2c9b92bf26a03eab4703ef124a481fd0c4cd798a4a6680b96daad
Timestamp: 1740155646 Timestamp [UCT]: 2025-02-21 16:34:06 Age [y:d:h:m:s]: 00:019:00:41:16
Block: 1224173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13657 RingCT/type: yes/0
Extra: 01b55b23e0dfb2c9b92bf26a03eab4703ef124a481fd0c4cd798a4a6680b96daad021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b9dd78a87747ea9e30ffa209b4e3dc32a1f5156252d634c5321d239f30f3eb5 0.600000000000 1711030 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": 1224183, "vin": [ { "gen": { "height": 1224173 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b9dd78a87747ea9e30ffa209b4e3dc32a1f5156252d634c5321d239f30f3eb5" } } ], "extra": [ 1, 181, 91, 35, 224, 223, 178, 201, 185, 43, 242, 106, 3, 234, 180, 112, 62, 241, 36, 164, 129, 253, 12, 76, 215, 152, 164, 166, 104, 11, 150, 218, 173, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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