Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ce0cf013a8b059a0f7ee2f5c57cfabb83b0cc549f5b9276a542bc104755d0d4

Tx prefix hash: 2b59a573a937492256b46461b3cf0e2be0b784d2a5f81373fc9ba31479bda93a
Tx public key: 8437f5321bbd5a4837cf2c430a1d93aa1b0fb86335d5d7ff1a3dd8b4a3c0ec87
Timestamp: 1701932561 Timestamp [UCT]: 2023-12-07 07:02:41 Age [y:d:h:m:s]: 01:133:17:55:14
Block: 907770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356739 RingCT/type: yes/0
Extra: 018437f5321bbd5a4837cf2c430a1d93aa1b0fb86335d5d7ff1a3dd8b4a3c0ec87021100000004c5452960000000000000000000

1 output(s) for total of 0.602810945000 dcy

stealth address amount amount idx
00: 668c00a394c5f28d7993f4550669fe16db63d21e17c89867e1316311d01ab137 0.602810945000 1364763 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": 907780, "vin": [ { "gen": { "height": 907770 } } ], "vout": [ { "amount": 602810945, "target": { "key": "668c00a394c5f28d7993f4550669fe16db63d21e17c89867e1316311d01ab137" } } ], "extra": [ 1, 132, 55, 245, 50, 27, 189, 90, 72, 55, 207, 44, 67, 10, 29, 147, 170, 27, 15, 184, 99, 53, 213, 215, 255, 26, 61, 216, 180, 163, 192, 236, 135, 2, 17, 0, 0, 0, 4, 197, 69, 41, 96, 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