Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78bf63e09d61c7e7e28af34defdeb1377b5842c883896e83d9d72a98b68233b1

Tx prefix hash: c2d8ab7275652eabd10185a516abacf24118419c51b5e021adf7672215c5f1fb
Tx public key: bdbc291327e907441b32f2234d69e33e5748f39aba8522aa8e990af457330f7a
Timestamp: 1581096170 Timestamp [UCT]: 2020-02-07 17:22:50 Age [y:d:h:m:s]: 04:361:04:23:12
Block: 60750 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1149299 RingCT/type: yes/0
Extra: 01bdbc291327e907441b32f2234d69e33e5748f39aba8522aa8e990af457330f7a02110000001f4ac5aa02000000000000000000

1 output(s) for total of 386.116491292000 dcy

stealth address amount amount idx
00: 228f538f58be02e1a41c126a7d68a054a196aef086f1b10df0125604bdee1dab 386.116491292000 111853 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": 60760, "vin": [ { "gen": { "height": 60750 } } ], "vout": [ { "amount": 386116491292, "target": { "key": "228f538f58be02e1a41c126a7d68a054a196aef086f1b10df0125604bdee1dab" } } ], "extra": [ 1, 189, 188, 41, 19, 39, 233, 7, 68, 27, 50, 242, 35, 77, 105, 227, 62, 87, 72, 243, 154, 186, 133, 34, 170, 142, 153, 10, 244, 87, 51, 15, 122, 2, 17, 0, 0, 0, 31, 74, 197, 170, 2, 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