Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 553c0413c02833da9d74f8e6df11f1a60a6ec9dd80e38ca3ccb3e8f0c0376696

Tx prefix hash: 1e0e8e97a94a8be0d0833ea1022ca94735f61bf22f5f9f43794b33707838d0aa
Tx public key: 4fb84f257fcf88bc31adb684d5e87325bd42f036a007bed6e9c225364d39e6d8
Timestamp: 1653606913 Timestamp [UCT]: 2022-05-26 23:15:13 Age [y:d:h:m:s]: 02:261:18:49:02
Block: 509610 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 707491 RingCT/type: yes/0
Extra: 014fb84f257fcf88bc31adb684d5e87325bd42f036a007bed6e9c225364d39e6d8021100000005faf35c9c000000000000000000

1 output(s) for total of 12.573341524000 dcy

stealth address amount amount idx
00: 00babcd8f90331ea355df83a920f38316f1c8b274f36a83c258ff09321a1a7fd 12.573341524000 935797 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": 509620, "vin": [ { "gen": { "height": 509610 } } ], "vout": [ { "amount": 12573341524, "target": { "key": "00babcd8f90331ea355df83a920f38316f1c8b274f36a83c258ff09321a1a7fd" } } ], "extra": [ 1, 79, 184, 79, 37, 127, 207, 136, 188, 49, 173, 182, 132, 213, 232, 115, 37, 189, 66, 240, 54, 160, 7, 190, 214, 233, 194, 37, 54, 77, 57, 230, 216, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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