Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe7dbb4e953d47d06cde19099f956ef4a103686f557a19d7ba2a78b04c399736

Tx prefix hash: 55ec2bdc2d9d9b2e58699cadfa84b64377d6b95893f98da4be586460c81562ba
Tx public key: 8772da6b4c495f6bd303d45833bf0ef6df6e6518edb51ee24d9039eefe5c8cae
Timestamp: 1724979372 Timestamp [UCT]: 2024-08-30 00:56:12 Age [y:d:h:m:s]: 01:062:15:50:16
Block: 1098831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303229 RingCT/type: yes/0
Extra: 018772da6b4c495f6bd303d45833bf0ef6df6e6518edb51ee24d9039eefe5c8cae02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 565c24ad0b57d91b553208b4f0fc5ee7056a09a053635fcb7efe7fb4556cd69e 0.600000000000 1574682 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": 1098841, "vin": [ { "gen": { "height": 1098831 } } ], "vout": [ { "amount": 600000000, "target": { "key": "565c24ad0b57d91b553208b4f0fc5ee7056a09a053635fcb7efe7fb4556cd69e" } } ], "extra": [ 1, 135, 114, 218, 107, 76, 73, 95, 107, 211, 3, 212, 88, 51, 191, 14, 246, 223, 110, 101, 24, 237, 181, 30, 226, 77, 144, 57, 238, 254, 92, 140, 174, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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