Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a82a031267e5146c870797bb3833d56c775e13b6baca585dfb7c599876bc110

Tx prefix hash: eb4162a4f349f9d3d232cda92f11064a8f0979ef5f122980a9e1db679fce46aa
Tx public key: fbec43cf181868a88e1f281767f5804e6a6d601aaf25e616e8d3e4941d98e66a
Timestamp: 1673024807 Timestamp [UCT]: 2023-01-06 17:06:47 Age [y:d:h:m:s]: 01:271:16:45:53
Block: 668966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 455214 RingCT/type: yes/0
Extra: 01fbec43cf181868a88e1f281767f5804e6a6d601aaf25e616e8d3e4941d98e66a02110000000452542ceb000000000000000000

1 output(s) for total of 3.727673787000 dcy

stealth address amount amount idx
00: bbdab6a5ad419fdff1d114f35df74e3faec85609d335778ce3cd5f4976b78122 3.727673787000 1110247 of 0

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": 668976, "vin": [ { "gen": { "height": 668966 } } ], "vout": [ { "amount": 3727673787, "target": { "key": "bbdab6a5ad419fdff1d114f35df74e3faec85609d335778ce3cd5f4976b78122" } } ], "extra": [ 1, 251, 236, 67, 207, 24, 24, 104, 168, 142, 31, 40, 23, 103, 245, 128, 78, 106, 109, 96, 26, 175, 37, 230, 22, 232, 211, 228, 148, 29, 152, 230, 106, 2, 17, 0, 0, 0, 4, 82, 84, 44, 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