Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34649e378b71e36178315e1616f054b6e870bcee04be94e5ca0188d0cad61f85

Tx prefix hash: 5eb80d7d41415b1b27f35be184a07d819db424cfa0a09575478c643631c02db8
Tx public key: 7c6c9ed5a96dafc2a8bca1bfbf3e88fdf36d054be751fdbce7549c5d591fc3c9
Timestamp: 1671381356 Timestamp [UCT]: 2022-12-18 16:35:56 Age [y:d:h:m:s]: 02:116:04:20:43
Block: 655392 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 604702 RingCT/type: yes/0
Extra: 017c6c9ed5a96dafc2a8bca1bfbf3e88fdf36d054be751fdbce7549c5d591fc3c902110000000375e3f0e9000000000000000000

1 output(s) for total of 4.134416417000 dcy

stealth address amount amount idx
00: 052c7d5654fc9d1c8cfbb162c6ae4826d5ef71be1a559def261c2482fd20ec74 4.134416417000 1095947 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": 655402, "vin": [ { "gen": { "height": 655392 } } ], "vout": [ { "amount": 4134416417, "target": { "key": "052c7d5654fc9d1c8cfbb162c6ae4826d5ef71be1a559def261c2482fd20ec74" } } ], "extra": [ 1, 124, 108, 158, 213, 169, 109, 175, 194, 168, 188, 161, 191, 191, 62, 136, 253, 243, 109, 5, 75, 231, 81, 253, 188, 231, 84, 156, 93, 89, 31, 195, 201, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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