Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f7728d1af18359181b28a885d9970a3de31b84cd7911b8c7387ce0c897d495f

Tx prefix hash: 7990a8ce80efcab83e68b7bd6d42c13efe0643722917e8fc718ec44a72534b1b
Tx public key: f2138eaaa3e80c50bb5e4c68af49269fc5a98eb6c68622b6894b155b3a4c6cb1
Timestamp: 1749446209 Timestamp [UCT]: 2025-06-09 05:16:49 Age [y:d:h:m:s]: 00:161:17:55:37
Block: 1301131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113279 RingCT/type: yes/0
Extra: 01f2138eaaa3e80c50bb5e4c68af49269fc5a98eb6c68622b6894b155b3a4c6cb1021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e621e3d1db16b56c3321cb6c0c8f7259d780bf9dffd635df0bd11eb055b78950 0.600000000000 1788684 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": 1301141, "vin": [ { "gen": { "height": 1301131 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e621e3d1db16b56c3321cb6c0c8f7259d780bf9dffd635df0bd11eb055b78950" } } ], "extra": [ 1, 242, 19, 142, 170, 163, 232, 12, 80, 187, 94, 76, 104, 175, 73, 38, 159, 197, 169, 142, 182, 198, 134, 34, 182, 137, 75, 21, 91, 58, 76, 108, 177, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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