Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc96b1f91ff6b34224035a1c33006518c0e897b98595eaafb1efb96b6a8e80ee

Tx prefix hash: 6fe3f9ad9feb214096b90ee61e8c2b556e0d7c542d5673e8f84cd8c428e8ad41
Tx public key: 677c64f5756ac6644dfc10b4cc4ca562505058518cd515707508ea441e439efa
Timestamp: 1712307091 Timestamp [UCT]: 2024-04-05 08:51:31 Age [y:d:h:m:s]: 01:217:07:33:34
Block: 993746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 414021 RingCT/type: yes/0
Extra: 01677c64f5756ac6644dfc10b4cc4ca562505058518cd515707508ea441e439efa02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4dbd4fa7cf340fa154c948c0f98f70d0cb7b5e04a9249264472e1b23624f34e9 0.600000000000 1454134 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": 993756, "vin": [ { "gen": { "height": 993746 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4dbd4fa7cf340fa154c948c0f98f70d0cb7b5e04a9249264472e1b23624f34e9" } } ], "extra": [ 1, 103, 124, 100, 245, 117, 106, 198, 100, 77, 252, 16, 180, 204, 76, 165, 98, 80, 80, 88, 81, 140, 213, 21, 112, 117, 8, 234, 68, 30, 67, 158, 250, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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