Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61b082fea6f045adb062244f73e3a0cc64390d89a8da4d29c37429eed3430283

Tx prefix hash: a2300e515fabd7855357cbda45aa580b238dc22b2d38c597d5947e49c8ebf350
Tx public key: 0e76c7225b227d6742771a06a7bdc3cd704fe12b84e4f89b4213ed0510c2029a
Timestamp: 1713112803 Timestamp [UCT]: 2024-04-14 16:40:03 Age [y:d:h:m:s]: 01:031:11:41:12
Block: 1000431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283483 RingCT/type: yes/0
Extra: 010e76c7225b227d6742771a06a7bdc3cd704fe12b84e4f89b4213ed0510c2029a02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f66c67ab16622e4982e4e2b639e9c7dfa3f6778fa86a3e612030ce00084569d 0.600000000000 1460929 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": 1000441, "vin": [ { "gen": { "height": 1000431 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f66c67ab16622e4982e4e2b639e9c7dfa3f6778fa86a3e612030ce00084569d" } } ], "extra": [ 1, 14, 118, 199, 34, 91, 34, 125, 103, 66, 119, 26, 6, 167, 189, 195, 205, 112, 79, 225, 43, 132, 228, 248, 155, 66, 19, 237, 5, 16, 194, 2, 154, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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