Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 955a15c8cb7287f1c426aff7a3c0650ff6eaa6b09ae39bf321ee8ab3bfe3b324

Tx prefix hash: f23456d449bab1d2e8a365045c8c02d9e74b7f3bf925d9912e78506714a1df4c
Tx public key: 734dd0ec76ba22a7e09a91eece4a084a40a1b85d67760b13b8171eb76cd441ec
Timestamp: 1703823671 Timestamp [UCT]: 2023-12-29 04:21:11 Age [y:d:h:m:s]: 01:100:13:04:34
Block: 923444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332960 RingCT/type: yes/0
Extra: 01734dd0ec76ba22a7e09a91eece4a084a40a1b85d67760b13b8171eb76cd441ec02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79b5861630a46263e79dbbc98a5e9c1e4e8effa249df73af1fc2a395db9d8a28 0.600000000000 1381176 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": 923454, "vin": [ { "gen": { "height": 923444 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79b5861630a46263e79dbbc98a5e9c1e4e8effa249df73af1fc2a395db9d8a28" } } ], "extra": [ 1, 115, 77, 208, 236, 118, 186, 34, 167, 224, 154, 145, 238, 206, 74, 8, 74, 64, 161, 184, 93, 103, 118, 11, 19, 184, 23, 30, 183, 108, 212, 65, 236, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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