Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52815130cdf2af108c3ac7eb7a90ddedfd4c65460710f53efc9eb5ef87ba4bbe

Tx prefix hash: fa20717dced0a0854c1a2a7bd2dd6d03e4755391d8c84a03eb501efc7f876a57
Tx public key: 9c43a2fef71004789cb4891942c6a776e51c9d72eb03f19cf23e925a0b519d34
Timestamp: 1706781731 Timestamp [UCT]: 2024-02-01 10:02:11 Age [y:d:h:m:s]: 01:142:03:40:12
Block: 947949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362529 RingCT/type: yes/0
Extra: 019c43a2fef71004789cb4891942c6a776e51c9d72eb03f19cf23e925a0b519d3402110000000d0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37156e8a08a35b59b130f21dd7deddd4eefe6e261b8f8ed8e5fc29ffced893e8 0.600000000000 1406311 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": 947959, "vin": [ { "gen": { "height": 947949 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37156e8a08a35b59b130f21dd7deddd4eefe6e261b8f8ed8e5fc29ffced893e8" } } ], "extra": [ 1, 156, 67, 162, 254, 247, 16, 4, 120, 156, 180, 137, 25, 66, 198, 167, 118, 229, 28, 157, 114, 235, 3, 241, 156, 242, 62, 146, 90, 11, 81, 157, 52, 2, 17, 0, 0, 0, 13, 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