Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf4a630bf9177292183a99640af37ad7b18b2675216173bf04ca542d03c801e7

Tx prefix hash: 8d638707b134c414b993709d982bfa1f96b8ae8135fefc2f3bd764ef32ee49e1
Tx public key: 1696c6d815960fe381f1b71e238ab6fce5f23dc9bd1e4ef5eb7ccb9fb78369d7
Timestamp: 1747846917 Timestamp [UCT]: 2025-05-21 17:01:57 Age [y:d:h:m:s]: 00:188:22:10:23
Block: 1287896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132721 RingCT/type: yes/0
Extra: 011696c6d815960fe381f1b71e238ab6fce5f23dc9bd1e4ef5eb7ccb9fb78369d70211000000061f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 92371ec93e32d831a6c469b508b586cc3bf12b424821e1425efdfb1a1505602d 0.600000000000 1775363 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": 1287906, "vin": [ { "gen": { "height": 1287896 } } ], "vout": [ { "amount": 600000000, "target": { "key": "92371ec93e32d831a6c469b508b586cc3bf12b424821e1425efdfb1a1505602d" } } ], "extra": [ 1, 22, 150, 198, 216, 21, 150, 15, 227, 129, 241, 183, 30, 35, 138, 182, 252, 229, 242, 61, 201, 189, 30, 78, 245, 235, 124, 203, 159, 183, 131, 105, 215, 2, 17, 0, 0, 0, 6, 31, 144, 81, 122, 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