Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b2a74ca51e3ef426a12f691a64a6ebe0180dc8e84541d445d25b226396a0d5a

Tx prefix hash: 07e09b927a6f1021e8c8eeb4c0806455cee49509f09f89ef1cc9f5062a19f821
Tx public key: 761d075bc591766ce6656c1b870db657551996384a248512ecd6fc983ad7d1ed
Timestamp: 1697364752 Timestamp [UCT]: 2023-10-15 10:12:32 Age [y:d:h:m:s]: 01:212:20:14:36
Block: 870100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413179 RingCT/type: yes/0
Extra: 01761d075bc591766ce6656c1b870db657551996384a248512ecd6fc983ad7d1ed021100000001faf35c9c000000000000000000

1 output(s) for total of 0.803521555000 dcy

stealth address amount amount idx
00: 2afa5785e27cb4d5a922bdf34e591c0988473530d74bf1ec2e9bd580c57a32ef 0.803521555000 1324973 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": 870110, "vin": [ { "gen": { "height": 870100 } } ], "vout": [ { "amount": 803521555, "target": { "key": "2afa5785e27cb4d5a922bdf34e591c0988473530d74bf1ec2e9bd580c57a32ef" } } ], "extra": [ 1, 118, 29, 7, 91, 197, 145, 118, 108, 230, 101, 108, 27, 135, 13, 182, 87, 85, 25, 150, 56, 74, 36, 133, 18, 236, 214, 252, 152, 58, 215, 209, 237, 2, 17, 0, 0, 0, 1, 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