Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 581fccee549bedd6bda4d9db50aa94825b8ef080d1261fc26b7ec392024e489f

Tx prefix hash: c961f62929e382921efcf29853d7e3cf5dcad51fa7f1cff8a52ae0e243692a4e
Tx public key: af0bb610cd1fd40eb430d76cfeaaa4ceffd22baf3c18954c39ac2f690efce318
Timestamp: 1583239921 Timestamp [UCT]: 2020-03-03 12:52:01 Age [y:d:h:m:s]: 04:257:11:09:11
Block: 75769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1078108 RingCT/type: yes/0
Extra: 01af0bb610cd1fd40eb430d76cfeaaa4ceffd22baf3c18954c39ac2f690efce318021100000142724f989b000000000000000000

1 output(s) for total of 344.307629192000 dcy

stealth address amount amount idx
00: 384b7d0e5438687eabe001b96ec85634740e20bf0ddebb598e90acfaaa51a28c 344.307629192000 139741 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": 75779, "vin": [ { "gen": { "height": 75769 } } ], "vout": [ { "amount": 344307629192, "target": { "key": "384b7d0e5438687eabe001b96ec85634740e20bf0ddebb598e90acfaaa51a28c" } } ], "extra": [ 1, 175, 11, 182, 16, 205, 31, 212, 14, 180, 48, 215, 108, 254, 170, 164, 206, 255, 210, 43, 175, 60, 24, 149, 76, 57, 172, 47, 105, 14, 252, 227, 24, 2, 17, 0, 0, 1, 66, 114, 79, 152, 155, 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