Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac75181275ee7b1dc0b1f37bf9bb8cc1c55f66774203df4e8ef7a04a07cfaf78

Tx prefix hash: 557ddb461bad9de904edab8f9e977cf47bb92d1cab613a073f096be39b2574a1
Tx public key: 66da1fdadd69f15298902f69d2dfd28219aebb2fad91e78e1ac1557c3a3513c7
Timestamp: 1707083719 Timestamp [UCT]: 2024-02-04 21:55:19 Age [y:d:h:m:s]: 01:023:22:00:53
Block: 950463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278125 RingCT/type: yes/0
Extra: 0166da1fdadd69f15298902f69d2dfd28219aebb2fad91e78e1ac1557c3a3513c70211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cbc923592e3eadff8f01ca97e9f3fdf790e8e9f10e5420c731e341a2661380a6 0.600000000000 1409091 of 15

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": 950473, "vin": [ { "gen": { "height": 950463 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cbc923592e3eadff8f01ca97e9f3fdf790e8e9f10e5420c731e341a2661380a6" } } ], "extra": [ 1, 102, 218, 31, 218, 221, 105, 241, 82, 152, 144, 47, 105, 210, 223, 210, 130, 25, 174, 187, 47, 173, 145, 231, 142, 26, 193, 85, 124, 58, 53, 19, 199, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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