Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0eacb3c58dd4f3bd024e650465f190c827d31970682a3d7a7a46fc51f14e2ad9

Tx prefix hash: bec9bce6915447da95e7b3f80525dabbb0d1b373d816a6224c36e08546c3ac4c
Tx public key: 9e2191e0a0951fa16b0688e31b79e45df9bcc56605b754d6693f8eef8d9198da
Timestamp: 1741876943 Timestamp [UCT]: 2025-03-13 14:42:23 Age [y:d:h:m:s]: 00:295:23:41:06
Block: 1238470 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209344 RingCT/type: yes/0
Extra: 019e2191e0a0951fa16b0688e31b79e45df9bcc56605b754d6693f8eef8d9198da02110000000e007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1ec55a7cee6823ca60a57f6728e3ddbf4bbef60dcc527e15cd4bd349957b902 0.600000000000 1725429 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": 1238480, "vin": [ { "gen": { "height": 1238470 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1ec55a7cee6823ca60a57f6728e3ddbf4bbef60dcc527e15cd4bd349957b902" } } ], "extra": [ 1, 158, 33, 145, 224, 160, 149, 31, 161, 107, 6, 136, 227, 27, 121, 228, 93, 249, 188, 197, 102, 5, 183, 84, 214, 105, 63, 142, 239, 141, 145, 152, 218, 2, 17, 0, 0, 0, 14, 0, 127, 151, 138, 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