Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a84f40fbdb3a47ddb31f6078b6be6b7952ae922ed13231106b48f4fcb306af1

Tx prefix hash: c861419f56ca2fe6be755fc18e48a03eb80d1a4606755992bc8fa9b808739147
Tx public key: fec26fe815170b1755ec7b383766a0eaeaf2e19b93be451cb29e1a5963aeddc2
Timestamp: 1581704181 Timestamp [UCT]: 2020-02-14 18:16:21 Age [y:d:h:m:s]: 05:086:15:05:37
Block: 65278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1214502 RingCT/type: yes/0
Extra: 01fec26fe815170b1755ec7b383766a0eaeaf2e19b93be451cb29e1a5963aeddc202110000000256c366d3000000000000000000

1 output(s) for total of 372.999026567000 dcy

stealth address amount amount idx
00: 292be5a0661cc1dcfeb16d81039a9f348f89dc73d0c870f3234b417731a8c5f6 372.999026567000 120309 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": 65288, "vin": [ { "gen": { "height": 65278 } } ], "vout": [ { "amount": 372999026567, "target": { "key": "292be5a0661cc1dcfeb16d81039a9f348f89dc73d0c870f3234b417731a8c5f6" } } ], "extra": [ 1, 254, 194, 111, 232, 21, 23, 11, 23, 85, 236, 123, 56, 55, 102, 160, 234, 234, 242, 225, 155, 147, 190, 69, 28, 178, 158, 26, 89, 99, 174, 221, 194, 2, 17, 0, 0, 0, 2, 86, 195, 102, 211, 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