Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fcf3e9944870ab00a0b12e48ec70ae3f7d526d64e4177b2471bf6c5f48ae81d

Tx prefix hash: eff5241e96f5f1c7e32ec36eb8ba445d302e7fb6d9d02b31346efd525a2a6ec2
Tx public key: 3934db6c11ae92f15eeaf27b0876c167296f1c075a258f91bb0a3e7b5eb41082
Timestamp: 1711360223 Timestamp [UCT]: 2024-03-25 09:50:23 Age [y:d:h:m:s]: 00:359:01:27:35
Block: 985957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256709 RingCT/type: yes/0
Extra: 013934db6c11ae92f15eeaf27b0876c167296f1c075a258f91bb0a3e7b5eb4108202110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 409b23fc40dd0a0fb62a8e15f5289243d552a6f935a0dbb4ed7ad0ae591a76d0 0.600000000000 1446178 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": 985967, "vin": [ { "gen": { "height": 985957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "409b23fc40dd0a0fb62a8e15f5289243d552a6f935a0dbb4ed7ad0ae591a76d0" } } ], "extra": [ 1, 57, 52, 219, 108, 17, 174, 146, 241, 94, 234, 242, 123, 8, 118, 193, 103, 41, 111, 28, 7, 90, 37, 143, 145, 187, 10, 62, 123, 94, 180, 16, 130, 2, 17, 0, 0, 0, 4, 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