Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd0e897a4c7b74e2691f007ab74ea07dd6a5cce859f8f30695eac33210d0bd97

Tx prefix hash: 963b3154235c757eb63f7286b04d1562478386e25d5a39d46ecafd3b588af45b
Tx public key: 0481423a5669c7932cb71c75886270d6b747f79084edc23270c4b5dcd8f21a1f
Timestamp: 1696124722 Timestamp [UCT]: 2023-10-01 01:45:22 Age [y:d:h:m:s]: 01:237:17:17:27
Block: 859814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 430997 RingCT/type: yes/0
Extra: 010481423a5669c7932cb71c75886270d6b747f79084edc23270c4b5dcd8f21a1f02110000000733af99f4000000000000000000

1 output(s) for total of 0.869119181000 dcy

stealth address amount amount idx
00: 3ea6633aa576ce25a579d6e4f4c75ad48b43a7bcce0ef2a8e19611f08a678c72 0.869119181000 1314062 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": 859824, "vin": [ { "gen": { "height": 859814 } } ], "vout": [ { "amount": 869119181, "target": { "key": "3ea6633aa576ce25a579d6e4f4c75ad48b43a7bcce0ef2a8e19611f08a678c72" } } ], "extra": [ 1, 4, 129, 66, 58, 86, 105, 199, 147, 44, 183, 28, 117, 136, 98, 112, 214, 183, 71, 247, 144, 132, 237, 194, 50, 112, 196, 181, 220, 216, 242, 26, 31, 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