Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd6abb779f95bfe70a9657f16b63f0e53020d8bf339ab6ebcb483c1abb909945

Tx prefix hash: c95d481577a01caa6637dc8225f9c011a12717ba5f961166005a980ec62c16d9
Tx public key: a1c8b8d202e79b210235fa0db61042f7f0dc5cc980644a04f39dbfd797c73609
Timestamp: 1729187544 Timestamp [UCT]: 2024-10-17 17:52:24 Age [y:d:h:m:s]: 00:041:11:51:01
Block: 1133731 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29614 RingCT/type: yes/0
Extra: 01a1c8b8d202e79b210235fa0db61042f7f0dc5cc980644a04f39dbfd797c73609021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1c1e10d5f01920ecb258b3fdc26e2caf9b5f8e40f6eafd85c0de716ef437a79 0.600000000000 1616922 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": 1133741, "vin": [ { "gen": { "height": 1133731 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1c1e10d5f01920ecb258b3fdc26e2caf9b5f8e40f6eafd85c0de716ef437a79" } } ], "extra": [ 1, 161, 200, 184, 210, 2, 231, 155, 33, 2, 53, 250, 13, 182, 16, 66, 247, 240, 220, 92, 201, 128, 100, 74, 4, 243, 157, 191, 215, 151, 199, 54, 9, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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