Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1d7a8d129508505d3f78d612c337b22dfa5d15798999f8b1b5e2b52ecb68e86

Tx prefix hash: c65b4430c693202632d9396ff81147e6ab99cc7c6557c9983dba377d4bc97d87
Tx public key: 229fe2207dc2053613c4915b9d67db2aa96d5dc2f215ea2bf06ebc4a2f89fafe
Timestamp: 1753082844 Timestamp [UCT]: 2025-07-21 07:27:24 Age [y:d:h:m:s]: 00:120:15:47:13
Block: 1330081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85046 RingCT/type: yes/0
Extra: 01229fe2207dc2053613c4915b9d67db2aa96d5dc2f215ea2bf06ebc4a2f89fafe02110000000a43846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f285190d0c1c420b771d8d304a1e42cb43b7f781cfed33ebfe4ff67833640527 0.600000000000 1817872 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": 1330091, "vin": [ { "gen": { "height": 1330081 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f285190d0c1c420b771d8d304a1e42cb43b7f781cfed33ebfe4ff67833640527" } } ], "extra": [ 1, 34, 159, 226, 32, 125, 194, 5, 54, 19, 196, 145, 91, 157, 103, 219, 42, 169, 109, 93, 194, 242, 21, 234, 43, 240, 110, 188, 74, 47, 137, 250, 254, 2, 17, 0, 0, 0, 10, 67, 132, 109, 102, 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