Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e4b03ed073c86b1212a4fd8d351a5e9ab2e46c18239eb4188b10d5bb7317fd9

Tx prefix hash: de806bf4f99063bd6ea551234c640c6e7e95a699352ccb814ea6a38fb67a1851
Tx public key: e1999431d99274e911579ed187a899f5263594023ce06dc6f8834eabf901d22b
Timestamp: 1673939994 Timestamp [UCT]: 2023-01-17 07:19:54 Age [y:d:h:m:s]: 02:037:18:49:27
Block: 676553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 548636 RingCT/type: yes/0
Extra: 01e1999431d99274e911579ed187a899f5263594023ce06dc6f8834eabf901d22b0211000000068b7b6602000000000000000000

1 output(s) for total of 3.518025703000 dcy

stealth address amount amount idx
00: 8aefbd1c1722c73f9ab6a932f0b9420969de6a0b054107fdf505257e873fb3fd 3.518025703000 1118274 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": 676563, "vin": [ { "gen": { "height": 676553 } } ], "vout": [ { "amount": 3518025703, "target": { "key": "8aefbd1c1722c73f9ab6a932f0b9420969de6a0b054107fdf505257e873fb3fd" } } ], "extra": [ 1, 225, 153, 148, 49, 217, 146, 116, 233, 17, 87, 158, 209, 135, 168, 153, 245, 38, 53, 148, 2, 60, 224, 109, 198, 248, 131, 78, 171, 249, 1, 210, 43, 2, 17, 0, 0, 0, 6, 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