Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4e65027f209b92932402f94e3776d79c6fda54945a0cd7719d4b09ab4011877

Tx prefix hash: 53d2a7c7e3269061d9fc916a0a88932fe82b41c4d845e87792afcb6aa12036c4
Tx public key: f992be056956a72d2e3ffa624161fc296a249e2d07d52044b526abb6f28b4c2f
Timestamp: 1635974318 Timestamp [UCT]: 2021-11-03 21:18:38 Age [y:d:h:m:s]: 03:363:02:12:31
Block: 366720 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1035537 RingCT/type: yes/0
Extra: 01f992be056956a72d2e3ffa624161fc296a249e2d07d52044b526abb6f28b4c2f02110000000b6a2c97e6000000000000000000

1 output(s) for total of 37.402859543000 dcy

stealth address amount amount idx
00: 1abda1d4f3388444388a2817d2856a67d4a11e584b6ec7d8f8633fa4d1a964cb 37.402859543000 744328 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": 366730, "vin": [ { "gen": { "height": 366720 } } ], "vout": [ { "amount": 37402859543, "target": { "key": "1abda1d4f3388444388a2817d2856a67d4a11e584b6ec7d8f8633fa4d1a964cb" } } ], "extra": [ 1, 249, 146, 190, 5, 105, 86, 167, 45, 46, 63, 250, 98, 65, 97, 252, 41, 106, 36, 158, 45, 7, 213, 32, 68, 181, 38, 171, 182, 242, 139, 76, 47, 2, 17, 0, 0, 0, 11, 106, 44, 151, 230, 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