Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe6854051f16d46ed8eff27aeffd9eb1b51f0bf059c8e4dfcc6165612085effa

Tx prefix hash: 5392747f569a4f43e78abc5ca5c95423324a83a404b9432b9deda568ec47f713
Tx public key: 5d5dfd7988e97d9fff760b8dfd136ea2957c6baafc2f4df24070bcebec84c2b4
Timestamp: 1629344449 Timestamp [UCT]: 2021-08-19 03:40:49 Age [y:d:h:m:s]: 02:324:17:10:59
Block: 316835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 744648 RingCT/type: yes/0
Extra: 015d5dfd7988e97d9fff760b8dfd136ea2957c6baafc2f4df24070bcebec84c2b402110000000cb75ebe6a000000000000000000

1 output(s) for total of 54.726110922000 dcy

stealth address amount amount idx
00: 1c7bc3a9e6b06360dec34c8d4db7f109e9ca951ffa9ee5afc0e63104a048d7e2 54.726110922000 659016 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": 316845, "vin": [ { "gen": { "height": 316835 } } ], "vout": [ { "amount": 54726110922, "target": { "key": "1c7bc3a9e6b06360dec34c8d4db7f109e9ca951ffa9ee5afc0e63104a048d7e2" } } ], "extra": [ 1, 93, 93, 253, 121, 136, 233, 125, 159, 255, 118, 11, 141, 253, 19, 110, 162, 149, 124, 107, 170, 252, 47, 77, 242, 64, 112, 188, 235, 236, 132, 194, 180, 2, 17, 0, 0, 0, 12, 183, 94, 190, 106, 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