Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0ba021ee6cab06e02b9fad503f63f13a208d65a99258501d05bbd00f97a72c2

Tx prefix hash: 86e1c72e9acf14b5dbd6a2ffdeac7118a30f4abe5f79643a8bf41df0c122d0b6
Tx public key: 973ae8ebb42dd1e259a56279dfa1a3deb00a3ec5ebd0c54ea03f370f90b4686d
Timestamp: 1722721273 Timestamp [UCT]: 2024-08-03 21:41:13 Age [y:d:h:m:s]: 00:173:07:48:23
Block: 1080115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123957 RingCT/type: yes/0
Extra: 01973ae8ebb42dd1e259a56279dfa1a3deb00a3ec5ebd0c54ea03f370f90b4686d021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d457445f788446f2551e8c2f9689b12e091b2de8bf149ee24b5da68c0f0a8d4 0.600000000000 1553350 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": 1080125, "vin": [ { "gen": { "height": 1080115 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d457445f788446f2551e8c2f9689b12e091b2de8bf149ee24b5da68c0f0a8d4" } } ], "extra": [ 1, 151, 58, 232, 235, 180, 45, 209, 226, 89, 165, 98, 121, 223, 161, 163, 222, 176, 10, 62, 197, 235, 208, 197, 78, 160, 63, 55, 15, 144, 180, 104, 109, 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