Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdbf54d7bcb1ca13b769aa96675b92f7a03829668e62d175bd46aae5c7d7d28b

Tx prefix hash: 80ba96c34010a6d569cffe4c93b1c1871345a9e194721e07c125327e82d6d80d
Tx public key: c5433c79ff4c9fafe7bf143e3ebaa4e85a68efa5d3498fb1ec7872592970da63
Timestamp: 1707841880 Timestamp [UCT]: 2024-02-13 16:31:20 Age [y:d:h:m:s]: 01:089:13:29:21
Block: 956752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325075 RingCT/type: yes/0
Extra: 01c5433c79ff4c9fafe7bf143e3ebaa4e85a68efa5d3498fb1ec7872592970da630211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 841806665f42fb3c4dab9b6a123a7dcf55b19c41355409e0bb183fd80d87f6a5 0.600000000000 1416062 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": 956762, "vin": [ { "gen": { "height": 956752 } } ], "vout": [ { "amount": 600000000, "target": { "key": "841806665f42fb3c4dab9b6a123a7dcf55b19c41355409e0bb183fd80d87f6a5" } } ], "extra": [ 1, 197, 67, 60, 121, 255, 76, 159, 175, 231, 191, 20, 62, 62, 186, 164, 232, 90, 104, 239, 165, 211, 73, 143, 177, 236, 120, 114, 89, 41, 112, 218, 99, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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