Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcea970894a23b017292133eb182de5e7b4712878dec2ea96e211a9e0f640883

Tx prefix hash: 959db28ccc093d6d353ef4d569bf99aa7897effd51b392dd6b1dbe4a79bca050
Tx public key: 585edddcb0eb62e525fd4009bd11cc193ceaf26a773a54a591657a63651197f9
Timestamp: 1696644513 Timestamp [UCT]: 2023-10-07 02:08:33 Age [y:d:h:m:s]: 01:097:10:56:14
Block: 864119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330919 RingCT/type: yes/0
Extra: 01585edddcb0eb62e525fd4009bd11cc193ceaf26a773a54a591657a63651197f902110000000f33af99f4000000000000000000

1 output(s) for total of 0.841036949000 dcy

stealth address amount amount idx
00: 57615b3181f531e773dc50b38ca854aac814f03aef5de0f8fc6129d02d6012be 0.841036949000 1318627 of 0

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": 864129, "vin": [ { "gen": { "height": 864119 } } ], "vout": [ { "amount": 841036949, "target": { "key": "57615b3181f531e773dc50b38ca854aac814f03aef5de0f8fc6129d02d6012be" } } ], "extra": [ 1, 88, 94, 221, 220, 176, 235, 98, 229, 37, 253, 64, 9, 189, 17, 204, 25, 60, 234, 242, 106, 119, 58, 84, 165, 145, 101, 122, 99, 101, 17, 151, 249, 2, 17, 0, 0, 0, 15, 51, 175, 153, 244, 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