Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66e875dcecad8655fc2b5bec090d5de4a3d43241d7cc3e75c4e1dda4c0422aa6

Tx prefix hash: bb9189ddea6680798579064105b533e3f1658e9699780da947d4b44a270822a7
Tx public key: b66113dc22fe04e8c9a4359075962876dca5fe105dcdfdd77a8edb8d42c4f65c
Timestamp: 1736817272 Timestamp [UCT]: 2025-01-14 01:14:32 Age [y:d:h:m:s]: 01:012:14:29:06
Block: 1196832 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267297 RingCT/type: yes/0
Extra: 01b66113dc22fe04e8c9a4359075962876dca5fe105dcdfdd77a8edb8d42c4f65c0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c4eb24b61a582da2c4dae9c7e8395b543691ae3afffdf06efaa39c7400fb43a 0.600000000000 1683435 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": 1196842, "vin": [ { "gen": { "height": 1196832 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c4eb24b61a582da2c4dae9c7e8395b543691ae3afffdf06efaa39c7400fb43a" } } ], "extra": [ 1, 182, 97, 19, 220, 34, 254, 4, 232, 201, 164, 53, 144, 117, 150, 40, 118, 220, 165, 254, 16, 93, 205, 253, 215, 122, 142, 219, 141, 66, 196, 246, 92, 2, 17, 0, 0, 0, 2, 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