Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fac09edef3716ef82191f547081b36b9878eec7283f15eacd9d1e50a401a90ec

Tx prefix hash: 58cd79b1e6479edee0f1a75b05a3688b311305a1f034d85b1a2c32e23c3c11e0
Tx public key: 5c42502f422d4008b9401473c96940ff15e14e59376929badac080a6e86479a0
Timestamp: 1728024765 Timestamp [UCT]: 2024-10-04 06:52:45 Age [y:d:h:m:s]: 01:034:06:20:02
Block: 1124089 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282863 RingCT/type: yes/0
Extra: 015c42502f422d4008b9401473c96940ff15e14e59376929badac080a6e86479a002110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4dc0e947fc070f5aee1a366f28f6fd8066263f09de3f7f388dd0fccf4112a5f 0.600000000000 1606656 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": 1124099, "vin": [ { "gen": { "height": 1124089 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4dc0e947fc070f5aee1a366f28f6fd8066263f09de3f7f388dd0fccf4112a5f" } } ], "extra": [ 1, 92, 66, 80, 47, 66, 45, 64, 8, 185, 64, 20, 115, 201, 105, 64, 255, 21, 225, 78, 89, 55, 105, 41, 186, 218, 192, 128, 166, 232, 100, 121, 160, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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