Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: faa9bd3623a6dc66e88916869be2663dec933e36c90a491cab655b52e64ec7fc

Tx prefix hash: 245980b97e23c877d3873671c6b3333c8058a0b3edfc8309448d24b3e9efc35e
Tx public key: 658d531e8db39c3cb7d6fdf80269f2a0c316d292eba9abe591a1fc14aa52dcd2
Timestamp: 1609170730 Timestamp [UCT]: 2020-12-28 15:52:10 Age [y:d:h:m:s]: 04:311:01:14:17
Block: 170918 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1233280 RingCT/type: yes/0
Extra: 01658d531e8db39c3cb7d6fdf80269f2a0c316d292eba9abe591a1fc14aa52dcd2021100000017a45716b1000000000000000000

1 output(s) for total of 166.608107351000 dcy

stealth address amount amount idx
00: 8b45793f3122c784fa62785436ea7d06da16591a4ed68337577b2233016d2a33 166.608107351000 321165 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": 170928, "vin": [ { "gen": { "height": 170918 } } ], "vout": [ { "amount": 166608107351, "target": { "key": "8b45793f3122c784fa62785436ea7d06da16591a4ed68337577b2233016d2a33" } } ], "extra": [ 1, 101, 141, 83, 30, 141, 179, 156, 60, 183, 214, 253, 248, 2, 105, 242, 160, 195, 22, 210, 146, 235, 169, 171, 229, 145, 161, 252, 20, 170, 82, 220, 210, 2, 17, 0, 0, 0, 23, 164, 87, 22, 177, 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