Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00c9831062e8257893e0d06fc91cfbf8037498711a5d7ca7d2b338075fd3915d

Tx prefix hash: f5cf3e8c5006a1bfb68b390855781449a9bb4e14d171a3584bbb83c14f3b572a
Tx public key: 1790a649a80a10866f6d963b9ebc86f014b3171beeb56ea2d4d13a4f3e840148
Timestamp: 1617100257 Timestamp [UCT]: 2021-03-30 10:30:57 Age [y:d:h:m:s]: 03:273:04:33:56
Block: 229648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 954721 RingCT/type: yes/0
Extra: 011790a649a80a10866f6d963b9ebc86f014b3171beeb56ea2d4d13a4f3e8401480211000000173634f08d000000000000000000

1 output(s) for total of 106.434255512000 dcy

stealth address amount amount idx
00: 1b915aaf8a7f69cb36004934897250e9d135e48c565060912a5787ccca16240d 106.434255512000 476566 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": 229658, "vin": [ { "gen": { "height": 229648 } } ], "vout": [ { "amount": 106434255512, "target": { "key": "1b915aaf8a7f69cb36004934897250e9d135e48c565060912a5787ccca16240d" } } ], "extra": [ 1, 23, 144, 166, 73, 168, 10, 16, 134, 111, 109, 150, 59, 158, 188, 134, 240, 20, 179, 23, 27, 238, 181, 110, 162, 212, 209, 58, 79, 62, 132, 1, 72, 2, 17, 0, 0, 0, 23, 54, 52, 240, 141, 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