Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17e54d73c21fe2bdb47c172da2743ac7b468651c8d7bfdc41281c1d4904162a2

Tx prefix hash: d758608870ae1070404b319d13d0f19ea82cea6c77253560f2dec35de4b2d33d
Tx public key: 7f2c4e06c614ac5a19a8fe579df96672959af65a8d986016efd6b6364b598ea6
Timestamp: 1720319070 Timestamp [UCT]: 2024-07-07 02:24:30 Age [y:d:h:m:s]: 00:270:23:40:04
Block: 1060198 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193607 RingCT/type: yes/0
Extra: 017f2c4e06c614ac5a19a8fe579df96672959af65a8d986016efd6b6364b598ea602110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c340ce612dd2980e8aabbc2da1fe13d6a87c25d3a3ba158e2936735ccf7d4fbb 0.600000000000 1530669 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": 1060208, "vin": [ { "gen": { "height": 1060198 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c340ce612dd2980e8aabbc2da1fe13d6a87c25d3a3ba158e2936735ccf7d4fbb" } } ], "extra": [ 1, 127, 44, 78, 6, 198, 20, 172, 90, 25, 168, 254, 87, 157, 249, 102, 114, 149, 154, 246, 90, 141, 152, 96, 22, 239, 214, 182, 54, 75, 89, 142, 166, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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