Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1089fcde676d9131f53ac904a3334444ee9b340b2f3c727fa84c57cb0b7a3cb8

Tx prefix hash: 6ae9144780a2f5e863fa36d48a7c653d56f229d31ae3b5f1b6f47f97cd7c2a46
Tx public key: 7b18421cf0fccc0e88ece1f11340a6879f267347658d3d90f2307e1b1e1296c9
Timestamp: 1668773431 Timestamp [UCT]: 2022-11-18 12:10:31 Age [y:d:h:m:s]: 02:209:18:23:45
Block: 633767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 671597 RingCT/type: yes/0
Extra: 017b18421cf0fccc0e88ece1f11340a6879f267347658d3d90f2307e1b1e1296c9021100000002272bcc39000000000000000000

1 output(s) for total of 4.876035402000 dcy

stealth address amount amount idx
00: 2af4ea5176b14c41b3088d5c7d0704a4a17ab7f032efa5ba47abfe9709b2c239 4.876035402000 1072887 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": 633777, "vin": [ { "gen": { "height": 633767 } } ], "vout": [ { "amount": 4876035402, "target": { "key": "2af4ea5176b14c41b3088d5c7d0704a4a17ab7f032efa5ba47abfe9709b2c239" } } ], "extra": [ 1, 123, 24, 66, 28, 240, 252, 204, 14, 136, 236, 225, 241, 19, 64, 166, 135, 159, 38, 115, 71, 101, 141, 61, 144, 242, 48, 126, 27, 30, 18, 150, 201, 2, 17, 0, 0, 0, 2, 39, 43, 204, 57, 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