Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 977f2a068cce2dfebd1fc893c6c124d76cb1236d613d0252e150345df9876c10

Tx prefix hash: 56a138b184785daed5df5e71815376bc20db09fe0d50c36d04094e111068442f
Tx public key: 17be0c176b6bf64536420cb775480c577b04f806b5f2a0f7d46aa7789aa5517e
Timestamp: 1673866884 Timestamp [UCT]: 2023-01-16 11:01:24 Age [y:d:h:m:s]: 02:041:13:20:40
Block: 675951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 551332 RingCT/type: yes/0
Extra: 0117be0c176b6bf64536420cb775480c577b04f806b5f2a0f7d46aa7789aa5517e0211000000018b7b6602000000000000000000

1 output(s) for total of 3.534220852000 dcy

stealth address amount amount idx
00: f949fd2687a5f4b7a2d46d5ab115e506ca0bdb07e158e1814185535e52018d0f 3.534220852000 1117642 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": 675961, "vin": [ { "gen": { "height": 675951 } } ], "vout": [ { "amount": 3534220852, "target": { "key": "f949fd2687a5f4b7a2d46d5ab115e506ca0bdb07e158e1814185535e52018d0f" } } ], "extra": [ 1, 23, 190, 12, 23, 107, 107, 246, 69, 54, 66, 12, 183, 117, 72, 12, 87, 123, 4, 248, 6, 181, 242, 160, 247, 212, 106, 167, 120, 154, 165, 81, 126, 2, 17, 0, 0, 0, 1, 139, 123, 102, 2, 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