Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94ee86380e0f8d81e02083926816a00879067c38c8e6b2c31eaafd7946fae781

Tx prefix hash: efd77ee41144d4fdfd2b8e36afb5439a15cd055fd96fb72c1ecb6f7d4c905fcd
Tx public key: e828cb0cd8b665308009292a379e6d9f98d2e152324b4d5c423d8cb3ee730e46
Timestamp: 1583531275 Timestamp [UCT]: 2020-03-06 21:47:55 Age [y:d:h:m:s]: 04:339:18:34:22
Block: 77652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1137252 RingCT/type: yes/0
Extra: 01e828cb0cd8b665308009292a379e6d9f98d2e152324b4d5c423d8cb3ee730e46021100000004e89b4e54000000000000000000

1 output(s) for total of 339.396596226000 dcy

stealth address amount amount idx
00: ec8c51b8ff05ff07c2017e32f56dcccb2cebddd01cc113b842e55528373c0da9 339.396596226000 142813 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": 77662, "vin": [ { "gen": { "height": 77652 } } ], "vout": [ { "amount": 339396596226, "target": { "key": "ec8c51b8ff05ff07c2017e32f56dcccb2cebddd01cc113b842e55528373c0da9" } } ], "extra": [ 1, 232, 40, 203, 12, 216, 182, 101, 48, 128, 9, 41, 42, 55, 158, 109, 159, 152, 210, 225, 82, 50, 75, 77, 92, 66, 61, 140, 179, 238, 115, 14, 70, 2, 17, 0, 0, 0, 4, 232, 155, 78, 84, 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