Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e33254ef6509ed6bcabbe4d798748d62e4182ccea91f64d9748287745ea6969a

Tx prefix hash: c3e40beb8dd457f46554a69b81cc15301be05361644ec0d7b1925876480715d6
Tx public key: d1d6a0c6145845d87bda370cac1891527c6a8eaf8fa0b8d01f89fd3c0d8a45ff
Timestamp: 1763020888 Timestamp [UCT]: 2025-11-13 08:01:28 Age [y:d:h:m:s]: 00:040:11:46:19
Block: 1411092 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28982 RingCT/type: yes/0
Extra: 01d1d6a0c6145845d87bda370cac1891527c6a8eaf8fa0b8d01f89fd3c0d8a45ff0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 731160102f122a52e39f527a9f1694a044a50b0696e3a60235bf655e7fe810b6 0.600000000000 1899549 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": 1411102, "vin": [ { "gen": { "height": 1411092 } } ], "vout": [ { "amount": 600000000, "target": { "key": "731160102f122a52e39f527a9f1694a044a50b0696e3a60235bf655e7fe810b6" } } ], "extra": [ 1, 209, 214, 160, 198, 20, 88, 69, 216, 123, 218, 55, 12, 172, 24, 145, 82, 124, 106, 142, 175, 143, 160, 184, 208, 31, 137, 253, 60, 13, 138, 69, 255, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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