Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4209adccf6826141d5d2ba78886d14006d934a8db0d7d1935c231a010083c849

Tx prefix hash: 1c1ca1984cb03137ba31cb54caca49232b2e54f9394e2a512ae04e050b81ed53
Tx public key: 06f87ec43edd12e6263ed2e37d907da15a40c6fb7043cbd49ca0e32543fb8c76
Timestamp: 1677161373 Timestamp [UCT]: 2023-02-23 14:09:33 Age [y:d:h:m:s]: 01:203:22:32:36
Block: 703279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406655 RingCT/type: yes/0
Extra: 0106f87ec43edd12e6263ed2e37d907da15a40c6fb7043cbd49ca0e32543fb8c7602110000000274b6d784000000000000000000

1 output(s) for total of 2.896613070000 dcy

stealth address amount amount idx
00: 6f3117555ad0e621e9565a6b242ceb98e6bde88709bccf48a2f5a25d94cb647d 2.896613070000 1146848 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": 703289, "vin": [ { "gen": { "height": 703279 } } ], "vout": [ { "amount": 2896613070, "target": { "key": "6f3117555ad0e621e9565a6b242ceb98e6bde88709bccf48a2f5a25d94cb647d" } } ], "extra": [ 1, 6, 248, 126, 196, 62, 221, 18, 230, 38, 62, 210, 227, 125, 144, 125, 161, 90, 64, 198, 251, 112, 67, 203, 212, 156, 160, 227, 37, 67, 251, 140, 118, 2, 17, 0, 0, 0, 2, 116, 182, 215, 132, 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