Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 930e8d6b2b46f5ad512fb47f7e471b519805e2a329ed6e42db90d993e03913a3

Tx prefix hash: 32f02016ff23923d251ede92d0f954d89178e2e23d41eec2010bdfe687548255
Tx public key: 7b137a7a680611b71a20ec18bc650d852179d780e7864d7d05480f3850e22ab3
Timestamp: 1731975575 Timestamp [UCT]: 2024-11-19 00:19:35 Age [y:d:h:m:s]: 01:028:14:33:14
Block: 1156750 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278892 RingCT/type: yes/0
Extra: 017b137a7a680611b71a20ec18bc650d852179d780e7864d7d05480f3850e22ab30211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf64fdfd241fc2622907451b2a2da4e1a32f2dacaa819b3c6dc587c2ebebb9d0 0.600000000000 1642373 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": 1156760, "vin": [ { "gen": { "height": 1156750 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf64fdfd241fc2622907451b2a2da4e1a32f2dacaa819b3c6dc587c2ebebb9d0" } } ], "extra": [ 1, 123, 19, 122, 122, 104, 6, 17, 183, 26, 32, 236, 24, 188, 101, 13, 133, 33, 121, 215, 128, 231, 134, 77, 125, 5, 72, 15, 56, 80, 226, 42, 179, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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