Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4a21b1181019ce9bd91fc3b338470b29ba5ed595f94f876cfd2c2595bd5d0c5

Tx prefix hash: fc01be0527c59d5d59dec55116c4c615b54c3597b62a1952098149964c6106a7
Tx public key: 7fadffad1b673d8315034ec18ccd3b3918f421dbf3dd30844eb4421b37a8de9e
Timestamp: 1634744486 Timestamp [UCT]: 2021-10-20 15:41:26 Age [y:d:h:m:s]: 03:040:08:54:03
Block: 356889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 807022 RingCT/type: yes/0
Extra: 017fadffad1b673d8315034ec18ccd3b3918f421dbf3dd30844eb4421b37a8de9e02110000001636fe6557000000000000000000

1 output(s) for total of 40.316145587000 dcy

stealth address amount amount idx
00: 012d2116cf7a0fa0da207441a8f1489a4202ba8bb088163e5c4eefd08ee45bb7 40.316145587000 727965 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": 356899, "vin": [ { "gen": { "height": 356889 } } ], "vout": [ { "amount": 40316145587, "target": { "key": "012d2116cf7a0fa0da207441a8f1489a4202ba8bb088163e5c4eefd08ee45bb7" } } ], "extra": [ 1, 127, 173, 255, 173, 27, 103, 61, 131, 21, 3, 78, 193, 140, 205, 59, 57, 24, 244, 33, 219, 243, 221, 48, 132, 78, 180, 66, 27, 55, 168, 222, 158, 2, 17, 0, 0, 0, 22, 54, 254, 101, 87, 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