Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2fc3545520d5a330126d388d85f0f05a234fd66568d53f1a0b91b7076b7f0fd

Tx prefix hash: 76815169c0c92c1fbb7761604986199380673372725c6beef35c27875a1a9cb6
Tx public key: 667dea17028fae61c90c0734bca844b7bdb0dceb43cc425001180cdc01d5d2aa
Timestamp: 1698574611 Timestamp [UCT]: 2023-10-29 10:16:51 Age [y:d:h:m:s]: 01:227:19:24:52
Block: 880147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 423796 RingCT/type: yes/0
Extra: 01667dea17028fae61c90c0734bca844b7bdb0dceb43cc425001180cdc01d5d2aa021100000002faf35c9c000000000000000000

1 output(s) for total of 0.744230793000 dcy

stealth address amount amount idx
00: 8cd16c1d07d8ed56eb48010a4a0bb06b45ac5b171a7c89fd7404affda0985a67 0.744230793000 1335693 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": 880157, "vin": [ { "gen": { "height": 880147 } } ], "vout": [ { "amount": 744230793, "target": { "key": "8cd16c1d07d8ed56eb48010a4a0bb06b45ac5b171a7c89fd7404affda0985a67" } } ], "extra": [ 1, 102, 125, 234, 23, 2, 143, 174, 97, 201, 12, 7, 52, 188, 168, 68, 183, 189, 176, 220, 235, 67, 204, 66, 80, 1, 24, 12, 220, 1, 213, 210, 170, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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