Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89f29e57608d752b2f6ae11fd55e53ec1c0efc920f614f5a5ec1028000dc6aee

Tx prefix hash: f6d3b320a83a5ac203db5808234f5842d0e1c3501f7a3ea2a19fc3bcde682e9f
Tx public key: 229c6c5630ebea8b4db9da818a1f9a6fa2d74c943db413b22badb2f5030d78a5
Timestamp: 1681395990 Timestamp [UCT]: 2023-04-13 14:26:30 Age [y:d:h:m:s]: 01:361:19:08:08
Block: 737747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 519865 RingCT/type: yes/0
Extra: 01229c6c5630ebea8b4db9da818a1f9a6fa2d74c943db413b22badb2f5030d78a50211000000015029cbac000000000000000000

1 output(s) for total of 2.205657915000 dcy

stealth address amount amount idx
00: ec9ba920616ef0b323dce7cd28ac93821265069ca7796a227b3d5e4bdb2f1264 2.205657915000 1184340 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": 737757, "vin": [ { "gen": { "height": 737747 } } ], "vout": [ { "amount": 2205657915, "target": { "key": "ec9ba920616ef0b323dce7cd28ac93821265069ca7796a227b3d5e4bdb2f1264" } } ], "extra": [ 1, 34, 156, 108, 86, 48, 235, 234, 139, 77, 185, 218, 129, 138, 31, 154, 111, 162, 215, 76, 148, 61, 180, 19, 178, 43, 173, 178, 245, 3, 13, 120, 165, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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