Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0583a37bc21b0b849793c66ace252ec184ed8e2a74680a4d72fa689e00e48ea1

Tx prefix hash: ac603d355361c705f1561fca2764d23d03b1e5ed3e0892c19d8eef561745d068
Tx public key: ff805e3c6e15a45f46ec0a013be511b1ff1548f04a98185d0863977c99df1d6f
Timestamp: 1743998832 Timestamp [UCT]: 2025-04-07 04:07:12 Age [y:d:h:m:s]: 00:223:15:21:11
Block: 1256001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157582 RingCT/type: yes/0
Extra: 01ff805e3c6e15a45f46ec0a013be511b1ff1548f04a98185d0863977c99df1d6f02110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 147f8154c1de18e2bda0141ee0c8e99e64bac3f41a8d2e9ac496f43fbeb35085 0.600000000000 1743110 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": 1256011, "vin": [ { "gen": { "height": 1256001 } } ], "vout": [ { "amount": 600000000, "target": { "key": "147f8154c1de18e2bda0141ee0c8e99e64bac3f41a8d2e9ac496f43fbeb35085" } } ], "extra": [ 1, 255, 128, 94, 60, 110, 21, 164, 95, 70, 236, 10, 1, 59, 229, 17, 177, 255, 21, 72, 240, 74, 152, 24, 93, 8, 99, 151, 124, 153, 223, 29, 111, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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