Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37f3f299157a84baf9a2c85f5d2a8d90df2e816457dc64c7c97d23ea0ba48aac

Tx prefix hash: 393f22bfdf7df0c52f9eb4dc7ae86ce615219e84cbf07522ea17a37758a0f94d
Tx public key: cd2803582e27412833c27e66484e0c27337fb4b94ac4d6310792c7d9b0fd8785
Timestamp: 1637260315 Timestamp [UCT]: 2021-11-18 18:31:55 Age [y:d:h:m:s]: 03:013:14:46:38
Block: 377129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 788483 RingCT/type: yes/0
Extra: 01cd2803582e27412833c27e66484e0c27337fb4b94ac4d6310792c7d9b0fd87850211000000161cab2639000000000000000000

1 output(s) for total of 34.547406828000 dcy

stealth address amount amount idx
00: 87b294d2c0e383658e08bb946601ffb3b915e4c26d785d3a074b1fb15b14ac22 34.547406828000 762847 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": 377139, "vin": [ { "gen": { "height": 377129 } } ], "vout": [ { "amount": 34547406828, "target": { "key": "87b294d2c0e383658e08bb946601ffb3b915e4c26d785d3a074b1fb15b14ac22" } } ], "extra": [ 1, 205, 40, 3, 88, 46, 39, 65, 40, 51, 194, 126, 102, 72, 78, 12, 39, 51, 127, 180, 185, 74, 196, 214, 49, 7, 146, 199, 217, 176, 253, 135, 133, 2, 17, 0, 0, 0, 22, 28, 171, 38, 57, 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