Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1307f1610de4684c2488ca335e04ea1a90725377e128f1e3d67f1a799638afc8

Tx prefix hash: 4cac30cd205f9df8f756b4cd35c7a626cd7db0587dc7ab4e8c2e2940c1dd80b9
Tx public key: 99ff906c91808712b38976bdf5a9624ce5e283e4cc84ab6b063859081331c70b
Timestamp: 1764099999 Timestamp [UCT]: 2025-11-25 19:46:39 Age [y:d:h:m:s]: 00:001:15:40:48
Block: 1420039 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1186 RingCT/type: yes/0
Extra: 0199ff906c91808712b38976bdf5a9624ce5e283e4cc84ab6b063859081331c70b021100000002d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e23d9ba93afc1beafc8315cc1a94feaa2948dc77cd8434fc0a575c07a629a02c 0.600000000000 1908580 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": 1420049, "vin": [ { "gen": { "height": 1420039 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e23d9ba93afc1beafc8315cc1a94feaa2948dc77cd8434fc0a575c07a629a02c" } } ], "extra": [ 1, 153, 255, 144, 108, 145, 128, 135, 18, 179, 137, 118, 189, 245, 169, 98, 76, 229, 226, 131, 228, 204, 132, 171, 107, 6, 56, 89, 8, 19, 49, 199, 11, 2, 17, 0, 0, 0, 2, 214, 225, 157, 124, 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