Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8a844552bd6891819ae4cf1ce0fca43414bf2b1b4d8e979ab8ad92004dd8fde

Tx prefix hash: 050643f15b4643952af0c3297b1d83a957e1af65e87cf4a6cd23a7f224691583
Tx public key: 5fe9559d74e2a61ad431a2b550eca5f7ab20e55b44c9204b3890707e0eea122d
Timestamp: 1705018616 Timestamp [UCT]: 2024-01-12 00:16:56 Age [y:d:h:m:s]: 01:148:00:17:45
Block: 933337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366929 RingCT/type: yes/0
Extra: 015fe9559d74e2a61ad431a2b550eca5f7ab20e55b44c9204b3890707e0eea122d0211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c4756a2e7650dc72092c47649a41a6cb0ee4fe6b9a04eae2f17d6c32604a9fc 0.600000000000 1391299 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": 933347, "vin": [ { "gen": { "height": 933337 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c4756a2e7650dc72092c47649a41a6cb0ee4fe6b9a04eae2f17d6c32604a9fc" } } ], "extra": [ 1, 95, 233, 85, 157, 116, 226, 166, 26, 212, 49, 162, 181, 80, 236, 165, 247, 171, 32, 229, 91, 68, 201, 32, 75, 56, 144, 112, 126, 14, 234, 18, 45, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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