Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 996f386b2df06defde06f7ad41a73c1948890ec29bcbe823008dd3f790313137

Tx prefix hash: 637f32b0b882a2b9c2ccd01821a66f28da00e9b23e97d64f54d879a4d5d8fd65
Tx public key: 5d65ae43baa6e9a43de22cf0b21470b4cca541ca2048f3f902cdfd98417334b0
Timestamp: 1579425491 Timestamp [UCT]: 2020-01-19 09:18:11 Age [y:d:h:m:s]: 05:137:00:12:36
Block: 48755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1248218 RingCT/type: yes/0
Extra: 015d65ae43baa6e9a43de22cf0b21470b4cca541ca2048f3f902cdfd98417334b0021100000002d81c26c0000000000000000000

1 output(s) for total of 423.111939584000 dcy

stealth address amount amount idx
00: 6de846f2b56b8a3a12e5f26c962af316248bcf89a36e0ba0e906a035aead007a 423.111939584000 90426 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": 48765, "vin": [ { "gen": { "height": 48755 } } ], "vout": [ { "amount": 423111939584, "target": { "key": "6de846f2b56b8a3a12e5f26c962af316248bcf89a36e0ba0e906a035aead007a" } } ], "extra": [ 1, 93, 101, 174, 67, 186, 166, 233, 164, 61, 226, 44, 240, 178, 20, 112, 180, 204, 165, 65, 202, 32, 72, 243, 249, 2, 205, 253, 152, 65, 115, 52, 176, 2, 17, 0, 0, 0, 2, 216, 28, 38, 192, 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