Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4a1e6bc454ee74172c1178000571725c4eef7af4c824347d8d66064ab9fd2e6

Tx prefix hash: ad0c5e4abfe85ce87c76ed3b42af7e4cd0923dcc610a8fbc1c3f9e29c4f7f2b0
Tx public key: aa634406f2ef959abe6712dd10ceea8c9ed07be9720ccf1d3d7e41f64a3525f5
Timestamp: 1576393314 Timestamp [UCT]: 2019-12-15 07:01:54 Age [y:d:h:m:s]: 05:015:08:04:43
Block: 27146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1157932 RingCT/type: yes/0
Extra: 01aa634406f2ef959abe6712dd10ceea8c9ed07be9720ccf1d3d7e41f64a3525f50211000000314943cd9f000000000000000000

1 output(s) for total of 498.962045963000 dcy

stealth address amount amount idx
00: 3f1e149c398a0392530c77e6a0c3ed883f6007511e20fc933045d83c4a6fcf25 498.962045963000 45019 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": 27156, "vin": [ { "gen": { "height": 27146 } } ], "vout": [ { "amount": 498962045963, "target": { "key": "3f1e149c398a0392530c77e6a0c3ed883f6007511e20fc933045d83c4a6fcf25" } } ], "extra": [ 1, 170, 99, 68, 6, 242, 239, 149, 154, 190, 103, 18, 221, 16, 206, 234, 140, 158, 208, 123, 233, 114, 12, 207, 29, 61, 126, 65, 246, 74, 53, 37, 245, 2, 17, 0, 0, 0, 49, 73, 67, 205, 159, 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