Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d7c910cbac4ff77cf396915ae8c9ce0f63c5152f8ac01c4aab41b5b7b84c744

Tx prefix hash: 14e8f36a627a23d7ee771f58b6787d36484ce147f70cc0acbfff23c6681b063f
Tx public key: 1d76303231be6bbccc6a5b5341728b737b06c9941c60565f78a861d270220d96
Timestamp: 1675049199 Timestamp [UCT]: 2023-01-30 03:26:39 Age [y:d:h:m:s]: 02:095:14:03:41
Block: 685789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 589944 RingCT/type: yes/0
Extra: 011d76303231be6bbccc6a5b5341728b737b06c9941c60565f78a861d270220d9602110000001d835e4d22000000000000000000

1 output(s) for total of 3.278659323000 dcy

stealth address amount amount idx
00: af6fcf37f6dbdfa7e0339abc09903cfaa8addc944962cad4ad6a5057916d7c4d 3.278659323000 1128176 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": 685799, "vin": [ { "gen": { "height": 685789 } } ], "vout": [ { "amount": 3278659323, "target": { "key": "af6fcf37f6dbdfa7e0339abc09903cfaa8addc944962cad4ad6a5057916d7c4d" } } ], "extra": [ 1, 29, 118, 48, 50, 49, 190, 107, 188, 204, 106, 91, 83, 65, 114, 139, 115, 123, 6, 201, 148, 28, 96, 86, 95, 120, 168, 97, 210, 112, 34, 13, 150, 2, 17, 0, 0, 0, 29, 131, 94, 77, 34, 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