Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6980262d8771018af00fa6266eba54e1d119473ed4cde6865c239bfc9e47630b

Tx prefix hash: 98f97f0feecdbb37a04a55da41352d47aa75fb56a568caeaec682028152070d9
Tx public key: 41ea09f33555f2fcecde64f82a91087e0e4d8b1d8fc9a974df34f74c29e22329
Timestamp: 1729952927 Timestamp [UCT]: 2024-10-26 14:28:47 Age [y:d:h:m:s]: 00:235:15:47:28
Block: 1140044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168110 RingCT/type: yes/0
Extra: 0141ea09f33555f2fcecde64f82a91087e0e4d8b1d8fc9a974df34f74c29e223290211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b452e2c005fc05b80cd513ea6acbc30d744ecb2867212c18ef319ab629ec61f3 0.600000000000 1623835 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": 1140054, "vin": [ { "gen": { "height": 1140044 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b452e2c005fc05b80cd513ea6acbc30d744ecb2867212c18ef319ab629ec61f3" } } ], "extra": [ 1, 65, 234, 9, 243, 53, 85, 242, 252, 236, 222, 100, 248, 42, 145, 8, 126, 14, 77, 139, 29, 143, 201, 169, 116, 223, 52, 247, 76, 41, 226, 35, 41, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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