Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5bd4230d087bd3e55fbf36a322ee416a1d65bc91328da447e99655aef4cd4815

Tx prefix hash: 0b1e0c62e6f44a0ecd64a962d6a3f58c335daaf953be6208ab306b4f60e6d1a9
Tx public key: 858a8e05a8fae9a50a58b4777b5c5529c5b51d92137ed54c6a7b2e631bed697a
Timestamp: 1668783243 Timestamp [UCT]: 2022-11-18 14:54:03 Age [y:d:h:m:s]: 02:059:09:23:30
Block: 633853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 564378 RingCT/type: yes/0
Extra: 01858a8e05a8fae9a50a58b4777b5c5529c5b51d92137ed54c6a7b2e631bed697a02110000000d74b6d784000000000000000000

1 output(s) for total of 4.872837136000 dcy

stealth address amount amount idx
00: 3b2882f53333b6e61694f358bf2f335c21a055cbea9e6bf63f574574ecbd4517 4.872837136000 1072985 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": 633863, "vin": [ { "gen": { "height": 633853 } } ], "vout": [ { "amount": 4872837136, "target": { "key": "3b2882f53333b6e61694f358bf2f335c21a055cbea9e6bf63f574574ecbd4517" } } ], "extra": [ 1, 133, 138, 142, 5, 168, 250, 233, 165, 10, 88, 180, 119, 123, 92, 85, 41, 197, 181, 29, 146, 19, 126, 213, 76, 106, 123, 46, 99, 27, 237, 105, 122, 2, 17, 0, 0, 0, 13, 116, 182, 215, 132, 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