Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a56235e05f94dfc5d6afec85ee3556ccad5db2a7b09f00980d888646c9044a77

Tx prefix hash: ae0e5747f2b6c2c32df0b201de1c1b29ad025897a9e6ca2e2f7bb1180cfb6873
Tx public key: 2849e84e128447e881165bbe030f9b6ce42f0d9fb34427a3e7fae26659322bf1
Timestamp: 1720245859 Timestamp [UCT]: 2024-07-06 06:04:19 Age [y:d:h:m:s]: 00:294:01:27:43
Block: 1059594 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210119 RingCT/type: yes/0
Extra: 012849e84e128447e881165bbe030f9b6ce42f0d9fb34427a3e7fae26659322bf10211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26c82f72c30799c64149331a10574c8a96ba7e7dcb1b77471faef28620a8bd1b 0.600000000000 1530063 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": 1059604, "vin": [ { "gen": { "height": 1059594 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26c82f72c30799c64149331a10574c8a96ba7e7dcb1b77471faef28620a8bd1b" } } ], "extra": [ 1, 40, 73, 232, 78, 18, 132, 71, 232, 129, 22, 91, 190, 3, 15, 155, 108, 228, 47, 13, 159, 179, 68, 39, 163, 231, 250, 226, 102, 89, 50, 43, 241, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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