Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 875b040795a01df58150602c641d527c182159414e5b8b16ab29cffa288164f5

Tx prefix hash: 5f0afec4d02a7b23bd04c0d5186f1d5d8dd8510366761d6a1d249de4aec24e70
Tx public key: 77cd6187c67417c25fcaea23cb584175c93b641e6c5f7a5f31443ff7c09659d3
Timestamp: 1732212359 Timestamp [UCT]: 2024-11-21 18:05:59 Age [y:d:h:m:s]: 00:002:12:42:10
Block: 1158703 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1813 RingCT/type: yes/0
Extra: 0177cd6187c67417c25fcaea23cb584175c93b641e6c5f7a5f31443ff7c09659d3021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9909f640686a0b87d36f32303f20bbfa6e153c80c1d7e0fc14ecb245e79cf879 0.600000000000 1644332 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": 1158713, "vin": [ { "gen": { "height": 1158703 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9909f640686a0b87d36f32303f20bbfa6e153c80c1d7e0fc14ecb245e79cf879" } } ], "extra": [ 1, 119, 205, 97, 135, 198, 116, 23, 194, 95, 202, 234, 35, 203, 88, 65, 117, 201, 59, 100, 30, 108, 95, 122, 95, 49, 68, 63, 247, 192, 150, 89, 211, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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