Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 907b860f585a3b99e2b687b852532a35d1e8067361b4caa0f8152795c9c6e812

Tx prefix hash: 52a27ad35cc65467903b48e2499ea4944caaeb358eb68c15444c129bc5030dfc
Tx public key: ef056881a94fa64e98c2f3c4a19517e2061bdc8042c58536ab1e188b547f38bb
Timestamp: 1755879879 Timestamp [UCT]: 2025-08-22 16:24:39 Age [y:d:h:m:s]: 00:095:22:37:10
Block: 1352093 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68516 RingCT/type: yes/0
Extra: 01ef056881a94fa64e98c2f3c4a19517e2061bdc8042c58536ab1e188b547f38bb021100000006ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a77f0d72f30bc9a8592f7b54d815e25a0384a9cac83c6d2b1df3d8b2286b3b91 0.600000000000 1840054 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": 1352103, "vin": [ { "gen": { "height": 1352093 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a77f0d72f30bc9a8592f7b54d815e25a0384a9cac83c6d2b1df3d8b2286b3b91" } } ], "extra": [ 1, 239, 5, 104, 129, 169, 79, 166, 78, 152, 194, 243, 196, 161, 149, 23, 226, 6, 27, 220, 128, 66, 197, 133, 54, 171, 30, 24, 139, 84, 127, 56, 187, 2, 17, 0, 0, 0, 6, 173, 121, 72, 208, 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