Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27f4037d8a6ba91343d4425ef148c588cfe0a8923b5041f98b404b6519cce5c5

Tx prefix hash: 5d34dc3364c7468608a3f0d4ef4b81d4a0dcd027ce17779a093c5cae458c2b16
Tx public key: 2aaf383fd1b04f5051f769b5e162fe611f3d453fd844dad7c1d54324689849cd
Timestamp: 1726662662 Timestamp [UCT]: 2024-09-18 12:31:02 Age [y:d:h:m:s]: 00:070:23:34:02
Block: 1112789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50752 RingCT/type: yes/0
Extra: 012aaf383fd1b04f5051f769b5e162fe611f3d453fd844dad7c1d54324689849cd021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29beeb7c61d500c8c200dd41825689fe0ae5ecde314bd969fd509555e9d58817 0.600000000000 1592232 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": 1112799, "vin": [ { "gen": { "height": 1112789 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29beeb7c61d500c8c200dd41825689fe0ae5ecde314bd969fd509555e9d58817" } } ], "extra": [ 1, 42, 175, 56, 63, 209, 176, 79, 80, 81, 247, 105, 181, 225, 98, 254, 97, 31, 61, 69, 63, 216, 68, 218, 215, 193, 213, 67, 36, 104, 152, 73, 205, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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