Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcc3e195f5275904cab87b4909429e754c1656220f3ee179d38005e9a1f960fb

Tx prefix hash: 21eefdec7c34e0a180f22601654f8dc04df76af628d9bb97bbc04c70c544c3b0
Tx public key: 6751dce094217e375d8fcae8321309d007db65b8acc91c1557649d8e7739c6a9
Timestamp: 1728435431 Timestamp [UCT]: 2024-10-09 00:57:11 Age [y:d:h:m:s]: 00:182:17:42:00
Block: 1127485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130394 RingCT/type: yes/0
Extra: 016751dce094217e375d8fcae8321309d007db65b8acc91c1557649d8e7739c6a9021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73d4a6c1da2ffd0f6b30303d2b8c549a0d5c446ddc3bf4de136039cca691776f 0.600000000000 1610292 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": 1127495, "vin": [ { "gen": { "height": 1127485 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73d4a6c1da2ffd0f6b30303d2b8c549a0d5c446ddc3bf4de136039cca691776f" } } ], "extra": [ 1, 103, 81, 220, 224, 148, 33, 126, 55, 93, 143, 202, 232, 50, 19, 9, 208, 7, 219, 101, 184, 172, 201, 28, 21, 87, 100, 157, 142, 119, 57, 198, 169, 2, 17, 0, 0, 0, 3, 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