Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b513ced4f3e3c550a6ecbb97a1107cc09cde431f45c220285b5dc24b7bede8db

Tx prefix hash: b81b62797fe93abbb527e0147f8c6da9e8dee1921a8bf89ea8f2d1d6e4dbae2c
Tx public key: ea290779414ebe173bb717aaea14aff8f442d487c5be07572eae80c5eff482b0
Timestamp: 1730813130 Timestamp [UCT]: 2024-11-05 13:25:30 Age [y:d:h:m:s]: 00:143:19:31:09
Block: 1147107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102621 RingCT/type: yes/0
Extra: 01ea290779414ebe173bb717aaea14aff8f442d487c5be07572eae80c5eff482b00211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3bc8e3e8cd55e8f6b1d8ea66fc805aa580e2f80372af96394b294cc1b60282f 0.600000000000 1631800 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": 1147117, "vin": [ { "gen": { "height": 1147107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3bc8e3e8cd55e8f6b1d8ea66fc805aa580e2f80372af96394b294cc1b60282f" } } ], "extra": [ 1, 234, 41, 7, 121, 65, 78, 190, 23, 59, 183, 23, 170, 234, 20, 175, 248, 244, 66, 212, 135, 197, 190, 7, 87, 46, 174, 128, 197, 239, 244, 130, 176, 2, 17, 0, 0, 0, 4, 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