Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0246e122bd41c1f93cd97104140508f334e7a6cb5c6955d9cd336c6d84a5d048

Tx prefix hash: beabb1252f2e425b21cbe73a8419a134f0e186e8274f768304cab0e243394b46
Tx public key: 2a879f18743a67c7e07a462e603e42cde5d0ff5350f8e4b445aa5ca66a64f533
Timestamp: 1721501472 Timestamp [UCT]: 2024-07-20 18:51:12 Age [y:d:h:m:s]: 00:282:06:29:52
Block: 1069998 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201685 RingCT/type: yes/0
Extra: 012a879f18743a67c7e07a462e603e42cde5d0ff5350f8e4b445aa5ca66a64f5330211000000010cce0636000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b69e1f2118fca13954948b09058decb10c9223c508034a7a91d2b66587fdb832 0.600000000000 1541653 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": 1070008, "vin": [ { "gen": { "height": 1069998 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b69e1f2118fca13954948b09058decb10c9223c508034a7a91d2b66587fdb832" } } ], "extra": [ 1, 42, 135, 159, 24, 116, 58, 103, 199, 224, 122, 70, 46, 96, 62, 66, 205, 229, 208, 255, 83, 80, 248, 228, 180, 69, 170, 92, 166, 106, 100, 245, 51, 2, 17, 0, 0, 0, 1, 12, 206, 6, 54, 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