Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 773943bea90f09a940c144085a575fbcb586e4731fa6fe2b38d593f1f0882b9d

Tx prefix hash: 3d398c90d0839767aab3768c9e5af6048c8375ceefe6622774f0ed7df71796cb
Tx public key: 24b4976e4c9f5246ec70c69cca5536bd27c616cb7910d53cc0c37780643da704
Timestamp: 1704359810 Timestamp [UCT]: 2024-01-04 09:16:50 Age [y:d:h:m:s]: 01:126:08:02:28
Block: 927894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351403 RingCT/type: yes/0
Extra: 0124b4976e4c9f5246ec70c69cca5536bd27c616cb7910d53cc0c37780643da70402110000000179bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ef3a0168dbd7ce2b8aae3e27ae58b33f36950e96e1269037c7f1f9e978e6934 0.600000000000 1385736 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": 927904, "vin": [ { "gen": { "height": 927894 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ef3a0168dbd7ce2b8aae3e27ae58b33f36950e96e1269037c7f1f9e978e6934" } } ], "extra": [ 1, 36, 180, 151, 110, 76, 159, 82, 70, 236, 112, 198, 156, 202, 85, 54, 189, 39, 198, 22, 203, 121, 16, 213, 60, 192, 195, 119, 128, 100, 61, 167, 4, 2, 17, 0, 0, 0, 1, 121, 189, 163, 190, 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