Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1478b43a8f1f729ac853bb83a83f898a8be06ca4d46f4207fbebe24b1f8f717d

Tx prefix hash: d3c6f4c4e71e712b3a631ddc41d9b82f3180e700167b3408e12e3da5b7e41813
Tx public key: f7cfbfb9d304f57f91ee0a7aad7d4553ef35174d8976e4ed9884988ea291b5fd
Timestamp: 1696106456 Timestamp [UCT]: 2023-09-30 20:40:56 Age [y:d:h:m:s]: 01:149:08:56:00
Block: 859664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367778 RingCT/type: yes/0
Extra: 01f7cfbfb9d304f57f91ee0a7aad7d4553ef35174d8976e4ed9884988ea291b5fd02110000000733af99f4000000000000000000

1 output(s) for total of 0.870114382000 dcy

stealth address amount amount idx
00: 4011c748b9b8c1facc83a0712f1b93b46edf5a41a39cc61fbff2c79b7566d625 0.870114382000 1313902 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": 859674, "vin": [ { "gen": { "height": 859664 } } ], "vout": [ { "amount": 870114382, "target": { "key": "4011c748b9b8c1facc83a0712f1b93b46edf5a41a39cc61fbff2c79b7566d625" } } ], "extra": [ 1, 247, 207, 191, 185, 211, 4, 245, 127, 145, 238, 10, 122, 173, 125, 69, 83, 239, 53, 23, 77, 137, 118, 228, 237, 152, 132, 152, 142, 162, 145, 181, 253, 2, 17, 0, 0, 0, 7, 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